Appendix - Troubleshooting Logi Log Files

When troubleshooting Logi, the first thing to try is setting the Debug Embedded Reports application setting to True (see the Application Settings: Console Tab in the Keyfactor Command Reference Guide). This allows the reports to output errors with debug level information if they generate errors. If this does not generate the information necessary to resolve the problem, it can sometimes be helpful to modify the Keyfactor Analysis web.config file to allow IIS to show the actual error the application is experiencing at a lower level. To configure this:

  1. Browse to the Logi directory under the installed directory for your Keyfactor Command implementation. By default, this is:
    C:\Program Files\Keyfactor\Keyfactor Platform\Logi
  2. Using a text editor opened with the "Run as administrator option, open the web.config file for editing.
  3. Find the <customErrors mode="RemoteOnly"/> section and change this to <customErrors mode="On"/>.
  4. Look for the debug output in the Logi\rdDownload directory under the installed directory for your Keyfactor Command implementation. By default, this is:
    C:\Program Files\Keyfactor\Keyfactor Platform\Logi\rdDownload
    5. Tip:  If you do not find debug output when running a report manually in the Management Portal, try scheduling a report for delivery via email or saving to disk using the Report Manager. Debugging operates differently for these two modes of running a report.
    Note:  When the portal experiences a 500 error, Logi logs will not be written to the usual output directory.

    Figure 527: Logi web.config